Import Requirements from CSV or Excel

The Import Requirements dialog guides you through all necessary steps. You can skip steps and jump back to steps. The following list gives you an overview about the steps:

Choose importer

Select File to import CSV and Excel files.

Select a requirements file to be imported

File

Source file

Select either CSV, XLSX, or XLS file.

Enter document version manually

If your requirements document does not contain a column that can be assigned to the Documentation version column in TPT, you can enter the version manually.

Import attachments

(optional) This check box is only enabled when a folder with attachment files has been detected. Select this check box to import attachments, see Import Requirement Attachments to TPT.

Configure raw data importer

XLSX or XLS file import

Import requirements from an Excel file to TPT

Sheet

If your file contains several worksheets, select one of it from the drop-down list.

First line is header

Select this check box to treat the first line of your worksheet file as header.

Check for hyperlinks

Select this check box to resolve Excel links like HYPERLINK("link_location"; "link text"). An additional column is generated with the hyperlinks. Link this additional column to the Requirement URI column in a later step to add the clickable link to the requirement.

Check for hyperlinks

Range

All used cells

By default, all cells with content are taken into account.

Start from "ID"

To consider only the columns following the ID column, select this option.

Manual input

To enter the range in the Range field manually, select this option.

CSV file import

Requirements import from a CSV file

Select a Delimiter (comma, semicolon, tab, space, custom character), the Encoding (ISO-8859-1, windows-1252, US-ASCII, UTF-8), and a Quote character (double quote, single quote, custom character).

First line is header

Select this check box to treat the first line of your CSV file as header.

Requirement ID

Select a column by name from the drop-down list or click on the column in the Imported source content. To deselect a column from the Imported source content, click the column again.

Requirement IDs must be globally unique. Old TPT files with double requirement IDs can no longer be loaded.

Select the requirement ID column

Requirement text

Select one column by name from the drop-down list. Or click on one or more columns in the Imported source content to select multiple columns. The content of the selected columns will be concatenated. To deselect a column from the Imported source content, click the column again. The requirement text column will be displayed in the test report.

Select the columns which content will be displayed as requirement text in TPT

Requirement URI

Select a column by name from the drop-down list or click on the column in the Imported source content. To deselect a column from the Imported source content, click the column again. The imported URIs will be used to create hyperlinks in the requirements table. In the test report, the ID name is clickable when a hyperlink was imported with the requirement.

Select the column which content will be displayed as requirement URI in TPT

Requirement type

TPT distinguishes between heading, information, and requirement. A requirement with the object type heading or information is used to structure requirements. They are never linked to a variant or test case and should therefore not be considered in the requirements statistics.

To tell TPT to treat those structuring requirements differently and ignore them in the requirements statistics, you must assign them to the TPT internal object types Heading or Information. Select a column by name from the drop-down list or click on the column in the Imported source content. Assign the different types to either Requirement, Heading, or Information, or Ignore them. If no type is assigned, all objects are regarded as requirements. To deselect a column from the Imported source content, click again on it.

Select a requirement type column and assign its content to TPT requirement types

The requirements of type Heading or Information can be displayed in the table in the Requirements Results section in the test report, see Execution Configuration - Report Settings: Requirements. Heading objects are displayed in a bold font and underlined in the requirements table in the Requirements view in TPT; information objects are displayed dimmed, and requirements are displayed unformatted.

Heading and information are treated as text objects in TPT

Document version

This dialog is only available when you haven't selected the Enter document version manually checkbox at the Choose Importer dialog. The document version number is bound to the requirement, that is, the imported requirements can have different document version numbers. A changed version number will be regarded as minor change by TPT and is therefore automatically set to "reviewed"; see also Modifications Tracing - Review Modifications. Select a column to retrieve the version of the document.

Document version

Document version column

To add the document version as an additional information, select a column by name from the drop-down list or click on the column in the Imported source content. The first non-empty value of the selected column will serve as the document version number. To deselect a column from the Imported source content, click the column again. Leave this setting empty to keep the current version.

Indentation level

(optional) Select a column by name from the drop-down list or click on the column in the Imported source content to indent the requirements in the requirements table in TPT. Non-integer and negative values will be ignored. To show/hide the indentation in the requirements table, click Toggle requirement text indentation. Changes regarding the indentation level are automatically reviewed.

Select a column with integer values to indent the objects accordingly in TPT

Indentation of requirements in the TPT requirements table

Links to test cases

Links between requirements and test cases can be updated.

Links column

Select the column with test case IDs, or click the column in the Imported source content table. To deselect the column, click the column again.

Test cases ID attribute

Select either TPT test case ID or the attribute which is specified in TPT and contains the external test case ID.

Several test case IDs must be added as a comma separated list.

Select a column to update the links to test cases

Newly imported links are created. Links that already exist in TPT but are not re-imported are deleted.

Test case attributes

(optional) Select one or more columns in the Imported source content to create additional attributes in the requirements table in TPT. To deselect a column from the Imported source content, click the column again.

Auto review

Click this check box to prevent your requirements from being marked as changed and all linked elements from being marked as to be reviewed in TPT when only minor changes have been made to the requirement.

You can access additional attributes of requirements in a Script assesslet by using REQUIREMENTS.get("id"), for example: REQUIREMENTS.get("SPEC-4").getAttribute("Product"), see Script Assesslet - Requirement Attributes. See also Assessment Type 'requirement'.

Select the columns you want to create additional attributes for

Main (bold font) and additional attributes in the Requirement details in TPT

Settings summary

Check your settings. To change a setting, use the Back button. Or click on the import step title in blue font.

Settings summary of the requirements import

Synchronize TPT requirements

Check the changes before applying the to TPT. The upper table shows all changed, unchanged, new requirements and also those that will be deleted. The requirements can be filtered according to their status (New, Unchanged, Changed, Deleted). Thus, to hide the unchanged requirements, deselect the Unchanged check box above the table. Click on the column name to sort the requirements. Double click on a requirement in the list, to open the Modifications view that shows the changes of the selected requirement.

Apply

By default, the Apply check box is selected at all NEW, CHANGED, and DELETED requirements. If you do not want to apply the change of a requirement, deselect the Apply check box at a requirement. For example, if you want to keep a requirement that would be deleted, deselect the Apply check box.

Status

New

If the import file contains a requirement with an ID that is not present in the current TPT project, this requirement is added to the project as NEW requirement .

Changed

If the requirement is already part of the current TPT project, TPT checks for differences. If differences are found, the imported file overwrites the content of the requirement in the current TPT project.

Double-click on a requirement to see what is going to be modified. See the Affected linked objects field for the test cases, state variants, and assesslets that are linked to the selected requirement and that might be affected by a change of the requirement content.

Modifications of the requirement SPEC-15

Unchanged

A requirement will be marked as UNCHANGED if it is identical to the requirement in your TPT project, or if only the Document Version differs.

Deleted

Requirements that are part of the current TPT project but are not found in the import file, are marked as to be DELETED . Such requirements are nevertheless part of your TPT project and are thus used during the test execution when the requirement is linked to a state variant, test case, or assesslet before the requirement has been marked as DELETED.

See the Affected linked objects field for the test cases, state variants, and assesslets that are linked to the selected requirement and that might be affected by the deletion of the requirement. Requirements that are marked as to be DELETED are displayed with their results in the report. You can recognize removed requirements in the report by the struck through requirements ID and the struck through object text.

Requirement SPEC-7 is marked as deleted in the report

Finally, a message is displayed containing the status and number of updated requirements.